Web Based Client/Server Notification Engine

ABSTRACT

Various technologies and techniques improve the updating of client content in a client/server arrangement. A client notification engine of a user interface subscribes to receive notifications from a central server side notification engine. The client notification engine polls the server side notification engine at a specified interval. The server side notification engine receives and aggregates notifications about and/or from one or more sources and aggregates them into a collection of relevant notifications. These notifications are sent to the client where the different subscriptions originated and are then used by the user interface in the client to update part of the content being displayed as appropriate.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application is a continuation of application Ser. No. 11/338,039,filed Jan. 24, 2006, which is incorporated herein by reference.

BACKGROUND

In today's world of technology, it has become easier than ever before tocommunicate with people using one or more of a variety of communicationmethods, such as email, telephone, fax, instant messaging, and so on.Communication and personal organizer programs typically have the abilityto display messages received from one or more of these various sources.Some communication programs operate in a web browser, such as MICROSOFT®Office OUTLOOK® Web Access (OWA), Yahoo Mail, AOL Mail, and others. Withsuch disconnected applications, the server is not contacted untilsomething is needed, such as when the user performs an action thatrequires the page to be updated or changed. When new communicationmessages are received on the server, the client is not updated with thenew content until the user selects an option to perform a manual refreshof the page's contents, or until the user otherwise takes some actioncausing the client to request that the server provide such updatedinformation.

SUMMARY

Various technologies and techniques are disclosed that improve theupdating of client content in a client/server arrangement. A clientnotification engine of a user interface, such as a communicationmanagement or email application, subscribes to receive notificationsfrom a server side notification engine. The client polls the server sidenotification engine at specified intervals. The server side notificationengine receives and aggregates notifications about and/or from one ormore sources and aggregates them into a collection of relevantnotifications at a specified interval. These notifications are sent tothe client where the different subscriptions originated and are thenused by the user interface in the client to update part of the contentbeing displayed as appropriate. In one implementation, a status bar isupdated to indicate that new communications have been received, such asa new email, a new fax, and/or a new voice mail. Alternatively oradditionally, a folder list is updated to display updated totals, suchas the number of unread messages in each folder or the number of totalitems in each folder. Alternatively or additionally, the contents of thefolder that the user is currently viewing are updated if they changed.

This Summary was provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagrammatic view of parts of a system of oneimplementation.

FIG. 2 is a diagrammatic view of additional parts of the system of FIG.1 of one implementation.

FIG. 3 is a high level process flow diagram for one implementation ofthe system of FIG. 1.

FIG. 4 is a logical diagram for one implementation of the system of FIG.1 illustrating the communications between the client side notificationengine and the front end server notification engine for subscribing toand managing notifications.

FIG. 5 is a process flow diagram for one implementation of the system ofFIG. 1 illustrating the stages involved in registering fornotifications, collecting notification responses, and processing theresponse received.

FIG. 6 is a simulated screen for one implementation of the system forFIG. 1 which illustrates allowing a user to specify messagingnotification options.

FIG. 7 is a simulated screen for one implementation of the system forFIG. 1 which illustrates allowing a user to specify remindernotification options.

FIG. 8 is a simulated screen for one implementation of the system forFIG. 1 which illustrates an email application with unread totals thatwere updated based on the subscription process of FIGS. 4 and 5.

FIG. 9 is a simulated screen for one implementation of the system forFIG. 1 which illustrates an email application with a status bar that wasupdated based on the subscription process of FIGS. 4 and 5.

FIG. 10 is a simulated screen for one implementation of the system forFIG. 1 which illustrates the new email message that was received whenthe user selects the New Mail option on the status bar of the simulatedscreen of FIG. 9.

FIG. 11 is a simulated screen for one implementation of the system forFIG. 1 which illustrates the new voice mail message that was receivedwhen the user selects the New Voice Mail option on the status bar of thesimulated screen of FIG. 9.

FIG. 12 is a simulated screen for one implementation of the system forFIG. 1 which illustrates the new fax message that was received when theuser selects the New Fax option on the status bar of the simulatedscreen of FIG. 9.

FIG. 13 is a simulated screen for one implementation of the system forFIG. 1 which illustrates the new calendar reminder that was receivedwhen the user selects the Reminders option on the status bar of thesimulated screen of FIG. 9.

DETAILED DESCRIPTION

For the purposes of promoting an understanding of the principles of theinvention, reference will now be made to the embodiments illustrated inthe drawings and specific language will be used to describe the same. Itwill nevertheless be understood that no limitation of the scope isthereby intended. Any alterations and further modifications in thedescribed embodiments, and any further applications of the principles asdescribed herein are contemplated as would normally occur to one skilledin the art.

The system may be described in the general context as a system thatimproves the updating of client content in a client/server arrangement.A client notification engine of a user interface subscribes to receivenotifications from a server side notification engine. The clientnotification engine polls the server side notification engine at aspecified interval. The server side notification engine receives andaggregates notifications about and/or from one or more sources and/ordata stores and aggregates them into a collection of relevantnotifications based on the context of the user. These notifications aresent to the client where the different subscriptions originated and arethen used by the user interface in the client to update part of thecontent being displayed as appropriate. A status bar or other area isupdated in the user interface to indicate that new communications havebeen received, such as a new email, a new fax, and/or a new voice mail.Alternatively or additionally, a folder list is updated to displayupdated totals, such as the number of unread messages in each folder orthe number of total items in each folder. Alternatively or additionally,the contents of the folder that the user is currently viewing areupdated if they changed.

The term folder as used herein is referring to any collection ofmessages, however they are stored and/or are represented in a graphicaluser interface. One of ordinary skill in the art will appreciate thatsome operating systems do not use the term folder when referring to acollection of messages, and that such scenarios are still covered by theexamples illustrated herein that use the term folder.

In one implementation, the system is a web-based communicationapplication such as MICROSOFT® Office OUTLOOK® Web Access (OWA), YahooMail, or AOL Mail. In another implementation, the system is any type ofcommunication application, web-based or not, that is not required tomaintain a constant connection to one or more data stores, such asMICROSOFT® Office OUTLOOK® and/or other email clients that support POP3and/or other disconnected message protocols. In yet anotherimplementation, the system is not a communication application, butserves other purposes, such as project scheduling, travel planning, orothers.

As shown in FIG. 1, an exemplary computer system to use for implementingone or more parts of the system includes one or more computing devices,such as computing devices 100, 130, and/or 150. In its most basicconfiguration, computing devices 100, 130, and/or 150 typically includeat least one processing unit (102, 132, and 152, respectively) andmemory (104, 134, and 154, respectively). Depending on the exactconfiguration and type of computing device, memory (104, 134, or 154)may be volatile (such as RAM), non-volatile (such as ROM, flash memory,etc.) or some combination of the two. This most basic configuration isillustrated in FIG. 1 by lines 106, 136, and 156.

Additionally, devices 100, 130, and/or 150 may also have additionalfeatures/functionality. For example, devices 100, 130, and/or 150 mayalso include additional storage (removable and/or non-removable)including, but not limited to, magnetic or optical disks or tape. Suchadditional storage is illustrated in FIG. 1 by removable storage (108,138, and 158, respectively) and non-removable storage (110, 140, and160, respectively). Computer storage media includes volatile andnonvolatile, removable and non-removable media implemented in any methodor technology for storage of information such as computer readableinstructions, data structures, program modules or other data. Memory(104, 134, and 154), removable storage (108, 138, and 158), andnon-removable storage (110, 140, and 160) are all examples of computerstorage media. Computer storage media includes, but is not limited to,RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM,digital versatile disks (DVD) or other optical storage, magneticcassettes, magnetic tape, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to store thedesired information and which can accessed by device 100, 130, and/or150. Any such computer storage media may be part of device 100, 130,and/or 150.

Computing devices 100, 130, and/or 150 include one or more communicationconnections that allow computing devices 100, 130, and/or 150 tocommunicate with each other and/or one or more other computing devicesover network 116. Communications connection(s) 114, 144, and 164 areexamples of communication media. Communication media typically embodiescomputer readable instructions, data structures, program modules orother data in a modulated data signal such as a carrier wave or othertransport mechanism and includes any information delivery media. Theterm “modulated data signal” means a signal that has one or more of itscharacteristics set or changed in such a manner as to encode informationin the signal. By way of example, and not limitation, communicationmedia includes wired media such as a wired network or direct-wiredconnection, and wireless media such as acoustic, RF, infrared and otherwireless media. The term computer readable media as used herein includesboth storage media and communication media.

In one implementation, computing device 100 is a client computer thatcommunicates with front end server computer 130 using communicationconnection 114 and 144 over network 116. In such an implementation, userinterface 118 of client computing device 100 communicates withnotification engine 148 on server computing device 130 to subscribe tonotifications and receive updated information. Front end server computer130 communicates with back end server computing device 150 by network116 using communication connections 144 and 164.

In one implementation, user interface 118 of client computing device 100is a browser-based user interface, such as MICROSOFT® Office OUTLOOK®Web Access (OWA), server computing device 130 is a web server, and backend server computing device 150 hosts a data store for a communicationprogram, such as MICROSOFT® Exchange. In another implementation, userinterface 118 of client computing device 100 is a user interfaceincluded in an executable program located on client computing device100, such as MICROSOFT® Office OUTLOOK®, MICROSOFT® Project, or LotusNotes. It will be appreciated that front end server computer 130 andback end server computing device 150 can be the same computer inalternate embodiments. Furthermore, it will be appreciated thatadditional back end server computing device 150 could also be used, suchas where multiple data stores are accessed by front end server computingdevice 130.

Computing devices 100, 130, and 150 may also have input device(s) (112,142, and 162, respectively) such as keyboard, mouse, pen, voice inputdevice, touch input device, etc. Output device(s) (111, 141, and 161,respectively) such as a display, speakers, printer, etc. may also beincluded. These devices are well known in the art and need not bediscussed at length here.

Turning now to FIG. 2 with continued reference to FIG. 1, a diagrammaticview of additional parts of system of FIG. 1 of one implementation areillustrated. The same reference numerals are used on FIG. 2 for thoseitems that are the same as on FIG. 1. Notification engine 119 of userinterface 118 on client computing device 100 communicates with centralnotification engine 148 of front end server computing device 130 tosubscribe to notifications. In one implementation, central notificationengine 148 has a notification manager class that contains methods forcreating one or more event queues, deleting an event queue, flushingand/or disposing of an event queue, creating a condition advisor,deleting a condition advisor, flushing and/or disposing of a conditionadvisor, creating a folder count advisor, deleting a folder countadvisor, flushing and/or disposing of a folder count advisor, and/orother methods for performing other operations.

Central notification engine 148 has an event queue object 180, acondition advisor object 182, and a count advisor object 184 that areoperable to communicate with one or more data stores 168 on one or moreback end server computing devices 150 to obtain updated information atspecified data gathering intervals. A few non-limiting examples of suchdata stores include one or more message stores or products such asMICROSOFT® Exchange, a POP3 or IMAP email data store, a fax data store,and/or another file or database. The updated information is thenaggregated by central notification engine 148 and returned tonotification engine 119 on client computing device 100 for furtherprocessing by user interface 118. In one implementation, only relevantinformation is returned, such as those specific to the context in whichthe user is working. As one non-limiting example, if the user iscurrently viewing his or her calendar, then detailed information aboutthe calendar would be returned, but detailed information about thecontents of the inbox would not be returned. In other implementations,more information is returned.

Turning now to FIG. 3 with continued reference to FIGS. 1 and 2, a highlevel process flow for one implementation is presented. In one form, theprocess of FIG. 3 is at least partially implemented in the operatinglogic of computing device 100, 130, and/or 150. The process begins atstart point 200 with the user logging into an email or other application(stage 202). Client computing device 100 retrieves notification settingsfor the particular user (stage 204). If notifications are not enabledfor the particular user (decision point 206), then the process ends atend point 214. If notifications are enabled for the particular user(decision point 206), then notification engine 119 of client computingdevice 100 communicates with central notification engine 148 on frontend server computing device 130 to register for notifications (stage208).

A few non-limiting examples of notifications include email messages,calendar reminders, task reminders, folder content changes, folder counttotals, etc. Notification engine 119 polls for and receivesnotifications that were aggregated by central notification service aboutwhat, if anything changed, updated totals (such as unread item counts),and/or some details about the changed and/or new content (stage 210).

In one implementation, the details about the changes and status of thevarious data that are received by the client are included in one or moretext files, such as XML. In another implementation, the details arereceived in a scripting language format, such as JavaScript or VBScript,where the script is executed and/or consumed by the notification engineon the client. In yet another implementation, the details are receivedin another file type or format for interpretation, execution, and/ordisplay on the client. User interface 118 interprets the informationreceived from the central notification engine and updates the userinterface display appropriately (stage 212). In one implementation,folder unread counts are updated to indicate the number of unreadmessages contained in that folder. Alternatively or additionally, astatus or indicator bar in the user interface is updated to displaywhether there are new reminders and/or new messages, such as new email,fax, voice messages, and/or reminders. Alternatively or additionally, acustom-defined rule can be defined by the user for display in the statusbar, such as to notify the user of any messages received from the boss.Alternatively or additionally, a folder the user is currently viewing isupdated with any new content relevant to the particular display.Alternatively or additionally, other content can also be stored locallyfor quick retrieval once the user changes context where the informationwould be needed. The process then ends at end point 214.

Turning now to FIG. 4 with continued reference to FIGS. 1 and 2, alogical diagram describing the process for subscribing to and managingnotifications in one implementation are illustrated. In one form, theprocess of FIG. 4 is at least partially implemented in the operatinglogic of computing device 100, 130, and/or 150. Client computing device100 registers for one or more notifications, such as remindernotifications (stage 240), folder tree unread count notifications (stage242), folder content change notifications (stage 244), and/or othernotifications (stage 246) with client side notification engine 248 (119on FIG. 2). Client side notification engine 248 registers fornotifications with front end server notification engine 256 (148 on FIG.2) and polls regularly (stage 252). Front end server notification engine256 manages event queues 258, condition advisors 260, folder countadvisor 262, and/or other information tracking objects 264.

Front end server notification engine 256 registers for notifications(stage 266) with one or more data stores 168 on back end servercomputing device(s) 268 (150 on FIG. 2). Back end server computingdevice 268 updates front end server notification engine 256 withnotifications periodically (stage 270). In other words, the eventqueue(s), content advisors, and item count advisors are updatedaccordingly. In one implementation, front end server notification engine256 combines the responses for all notification requests (stage 254) andreturns only the necessary ones (such as the relevant ones) to theclient side notification engine 248. The client side notification engine248 distributes notifications to user interface components and performsthe necessary actions (stage 250), such as to update the display.

Turning now to FIG. 5 with continued reference to FIGS. 1 and 2, thestages involved in registering for notifications, collectingnotification responses, and processing the response received in oneimplementation are illustrated. In one form, the process of FIG. 5 is atleast partially implemented in the operating logic of computing device100, 130, and/or 150. The process begins at start point 300 with theuser logging in to the application (stage 302). Client side notificationengine 248 of user interface 118 registers for notifications with thecentral notification engine 148. In one implementation, centralnotification engine 148 creates folder modified condition advisors forall folders, event queues for new notifications, such as in the Inbox,and/or folder item count advisors for some or all of the folders (stage304). If the session has not timed out or otherwise ended (decisionpoint 306), then the client notification engine 119 checks to determinewhether the polling interval time has passed (decision 308). The clientnotification engine 119 waits until the polling interval passes by(decision point 308) to poll the central notification engine 148 fornotifications (stage 310). If there are notifications to report(decision point 312), then the central notification engine 148 generatesa response based on the information in the event queue(s), conditionadvisors, and folder unread count advisor(s) and sends them to theclient side notification engine 248 for further processing by the userinterface 118 (stage 316). User interface 118 interprets and/orotherwise executes the response, and updates the appropriate userinterface views (stage 318).

If there are no notifications to report (decision point 312), then thecentral notification engine 148 generates an empty or blank response andsends it to the client side notification engine 248 (stage 314). Theprocess then repeats for each polling interval (decision point 308) oruntil the user session times out or the user closes the application(decision point 306). If the session times out or the user otherwiseends the session or application (decision point 306), such as by closingthe browser or program, then the event queue, condition advisors, andfolder unread count advisor objects are destroyed (stage 320) to free upsystem resources. The process then ends at end point 322.

FIG. 6 is a simulated screen 340 for one implementation of the systemfor FIG. 1 which illustrates allowing a user to specify messagingnotification options. The user can select whether to enable or disableoptions that display a notification message when new mail arrives 342,display a notification message when a new voice mail arrives 344,display a notification when new voice message arrives 346, and/or toplay a sound when new message arrives 348. In one implementation, if anyone or more of these options are enabled (decision point 206 on FIG. 3),then user interface 118 of client computing device 100 registers formessaging event notifications with central notification engine 148 onfront end server computing device 130.

FIG. 7 is a simulated screen 350 for one implementation of the systemfor FIG. 1 which illustrates allowing a user to specify remindernotification options. The user can select whether to enable or disableoptions that show reminder alerts for calendar items 352, show reminderalerts for task items 354, plays a sound when a reminder is due 356,and/or to set the default reminder time frame 358. In oneimplementation, if any one or more of options 352, 354, or 356 areenabled (decision point 206 on FIG. 3), then user interface 118 ofclient computing device 100 registers for reminder event notificationswith central notification engine 148 on front end server computingdevice 130.

After messaging and/or reminder notifications are registered withcentral notification engine 148, user interface 118 then waits for thepolling time to pass by (decision point 308), polls for and receivesaggregated notifications from the central notification engine 148 (stage310) and processes the response to update the user interface accordingly(stage 318).

Non-limiting examples of how the user interface 118 can be updated basedon the aggregated notifications are shown in simulated screens 8-13.FIG. 8 is a simulated screen 360 for one implementation of the systemfor FIG. 1 which illustrates an email application with unread totalsthat were updated based on the event subscription process of FIGS. 3-5.Simulated screen 360 is a browser-based communication/personal organizerapplication that has various folders, such as Inbox 364, one or moreuser defined folder(s), Deleted Items 366, Calendar 368, and/or otherfolders, for displaying information to the user and allowing the user tomanage his or her information and/or schedule. Upon receiving aggregatednotifications from central notification engine (stage 210), foldercounts are updated, such as “(7)” for Inbox 364, and/or others shown onscreen 360. In one implementation, the totals represent the total numberof unread items in the folder. In another implementation, the totalrepresents the total number of items in the folder. Alternatively oradditionally, the user interface can be updated automatically to displaynew content that is relevant to the context that the user is working in.For example, since the user has the Inbox folder 364 selected, newmessages can be displayed in message area 369 based upon a sort ordersetting specified by the user or by a system default setting.

As shown in FIG. 9, in one implementation, a status bar is updated basedon the aggregated notifications received from central notificationengine (stage 210). For example, status bar 377 on simulated screen 370includes four notification messages: New Email 375, New Voice Mail 371,New Fax 372, and New Reminder 373 that represent the type of newmessages and/or reminders (e.g. calendar and/or task reminders) thathave been received by the user. Other variations are also possible thatinclude some or additional message and/or reminder notifications thanthese. In one implementation, a Help option 374 is displayed in thestatus bar.

Turning now to FIG. 10, in one implementation, when the user selects theNew Email notification message 382 (or a particular notification) in thestatus bar of screen 380, a snippet of the message 384 is shown near thestatus bar area to give the user a preview of the message. In oneimplementation, the New Email notification message 382 (or selectednotification) then disappears after the user selects it from the statusbar area. In another implementation, the New Email notification message382 (or selected notification) is displayed until the user accesses themessage in the Inbox folder and causes the status of the message tochange to “read”.

Instead of or in addition to showing a snippet of the message 384 whenthe user selects New Email notification message 382, the snippet 384 canbe displayed for a specified period of time (such as 5 seconds) when thescreen is first updated. In another implementation, when the userselects New Email notification message 382, contents 386 of inbox folderare updated to include the new message(s). In yet anotherimplementation, contents 386 of inbox folder are updated automaticallywhen the aggregated notifications are received from the centralnotification engine 148. Other variations are also possible that includecombinations of these, fewer, and/or additional variations.

Similarly to FIG. 10, FIGS. 11-13 are simulated screens (390, 400, and410, respectively) for one implementation of the system for FIG. 1 whichillustrate what happens in the status bar area when the user selects theother options. For example, simulated screen 390 of FIG. 11 illustrateswhat happens in the status bar area when the user selects the New VoiceMail notification message 392. A snippet of the voice mail message 394appears near the status bar and includes details such as the caller'sphone number and the length of the message. Simulated screen 400 of FIG.12 illustrates an example of what happens in the status bar area whenthe user selects the New Fax notification message 402. A snippet of themessage 404 appears near the status bar and includes details such as thesender's fax number and/or the number of pages received. Alternativelyor additionally, simulated screen 410 of FIG. 13 illustrates an exampleof what happens in the status bar area when the user selects the NewReminders notification message 412. A snippet of the reminder message414 appears near the status bar and additional details about theappointment and/or task. In one implementation, calendar and taskreminders are grouped together in the same reminder area. In anotherimplementation, calendar reminders have a separate notification messageon the status bar from task reminders.

With respect to simulated screens 9-13, numerous other variations arealso possible for determining when and where to display the respectivesnippet, if at all. In some implementations, part or all of the detailsrelated to the message and/or reminder are displayed and/or audiblyrendered to the user in some fashion.

The examples in FIGS. 7-13 are for purposes of illustration only, andare not limiting in nature. For example, other variations are alsopossible, such as using the technologies and techniques discussed hereinfor receiving updated content from a server in applications other thancommunications programs, such as from a project planning application,such as MICROSOFT® Project. Other examples can include any type ofapplication that does not maintain a constant connection with the serverwhile a user is accessing the application.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are disclosed asexample forms of implementing the claims. All equivalents, changes, andmodifications that come within the spirit of the implementations asdescribed herein and/or by the following claims are desired to beprotected.

For example, a person of ordinary skill in the computer software artwill recognize that the client and/or server arrangements, userinterface screen content, and/or data layouts as described in theexamples discussed herein could be organized differently on one or morecomputers to include fewer or additional options or features than asportrayed in the examples.

1. A method for improving client-side content updates comprising: sending a registration from a computing system to a central notification engine to register for update notifications, the registration including information identifying a plurality of folders to monitor for changes; after sending the registration, sending a request from the computing system to the central notification engine for update notifications associated with the plurality of folders identified by the registration; if the central notification engine has notifications to report, receiving a notification response from the central notification engine, the notification response including an aggregation of updates from a first data store and a second data store; if the central notification engine has no notifications to report, receiving a notification response from the central notification engine after a polling interval expires, the notification response indicating that no updates have occurred.
 2. The method of claim 1, wherein the updates include two or more of the following: email, calendar, contacts, notes, or tasks.
 3. The method of claim 1, wherein the request comprises a polling request.
 4. The method of claim 1, wherein the computing system includes a client-side notification engine.
 5. The method of claim 1, further comprising, if the notification response includes the aggregation of updates, updating a user interface in response to receiving the notification response.
 6. The method of claim 1, wherein, if the central notification engine has notifications to report, the notification response includes a list of updated folders, the list identifying folders that have updated contents.
 7. The method of claim 1, wherein if the central notification engine has no notifications to report, the notification is an empty response message.
 8. The method of claim 1, wherein the notification response is represented in XML.
 9. The method of claim 1, further comprising generating a visible indication of the notification in a status bar on a display.
 10. The method of claim 1, wherein if the central notification engine has notifications to report, the notification response is received after the polling interval expires.
 11. The method of claim 1, wherein the aggregation of updates includes a number of items in at least one of the plurality of folders identified by the registration.
 12. A method executed at a central notification engine for updating content at a computing system, the method comprising: receiving a registration from a computing system at a central notification engine, the registration including information identifying a plurality of folders to monitor for changes; after receiving the registration, receiving a request from the computing system at the central notification engine for update notifications associated with the plurality of folders identified by the registration; if the central notification engine has notifications to report, transmitting a notification response from the central notification engine, the notification response including an aggregation of updates from a first data store and a second data store; if the central notification engine has no notifications to report, transmitting a notification response from the central notification engine after a polling interval expires, the notification response indicating that no updates have occurred.
 13. The method of claim 12, wherein the notifications are selected from the group consisting of an email message, a fax message, a voice mail message, and a reminder message.
 14. The method of claim 12, further comprising generating the notification response at the central notification engine, the notification response including information from at least one of a condition advisor and an item count advisor.
 15. The method of claim 14, further comprising checking at least the condition advisor and the item count advisor to determine whether there are notifications to report.
 16. The method of claim 14, wherein the condition advisor and item count advisor are associated with at least one of the plurality of folders identified by the registration.
 17. The method of claim 12, wherein if the central notification engine has no notifications to report, the notification is an empty response message transmitted to the computing system.
 18. The method of claim 12, wherein if the central notification engine has notifications to report, the notification response is transmitted after the polling interval expires.
 19. The method of claim 12, wherein the aggregation of updates includes a number of items in at least one of the plurality of folders identified by the registration.
 20. The method of claim 12, wherein the first data store and the second data store comprise first and second folders from among the plurality of folders identified in the request. 